Sometimes the C/S runs into the case whose attention is solidly fixed on something. When attention is fixed we have an unawareness of other things than the object of fixation and a lessening of self-determinism to a point of other determinism. Example: The pc is always bringing up cars. He has trouble with cars, has ARC breaks about cars, W/Hs about cars, commits overts on cars. It worries him all the time, is a constant problem.

The fixated attention case appears not to as-is and is usually stuck on the track in the "quiet" portion of an incident. Ahead of it and behind it is extreme randomity. This is not easily confronted so is not-ised. The solution is to get the pc to exercise his attention, putting it here and there.

The pc whose attention is fixated manifests it in several ways. He will be continuously introverted on the area, will bring it up often in session but it doesn't seem to blow. It also shows up in correspondence to the C/S, frequent originations at Examiner, a fixed vague stare, all evidence of introversion. The pc may not originate it.

This fixation shows up as a problem but it is usually a hidden standard, a special problem the pc thinks must be resolved before auditing can be seen to have worked. Hence the NCG (no case gain) aspect. It is always an old problem of long duration.

The remedy basically involves getting the terminal connected with the area of fixation located and having the pc put his attention on the terminal and take his attention off the terminal.

STEP 1 — Determine exactly what the pc has attention fixed on, by folder inspection or 2WC for a BD F/N item.

STEP 2 — Get the area translated into a terminal. This will read well and have a high degree of pc interest.

STEP 3 — Fit the terminal in the commands: "Put your attention on (terminal). "Take your attention off (terminal)." Clear and run it alternate repetitive to the EP of pc's attention no longer fixed on the area, F/N Cog VGIs. This is called Attention Subjective Repetitive.

STEP 4 — Select two objects. Best are a red pen and a blue pen. Two bowling pins will also do. Place them three to four feet apart at a distance of three to four feet from the pc. Place them on white paper for visibility.

STEP 5 — Name the objects and fit them in the commands: "Put your attention on the red pen." "Put your attention on the blue pen." Clear the commands and run them alternate repetitive to the EP of pc in control of his attention, F/N Cog VGIs. This is called Attention Objective Repetitive.

ALTERNATE STEP 5 — Name the objects and fit them in the following commands: "Decide to put your attention on the red pen. Tell me when you've done so." "Put your attention on it." Then "Decide to put your attention on the blue pen. Tell me when you've done so." "Put your attention on it." Run this alternate repetitive until the pc is doing the decision step each time, then you can drop out the "Tell me when you've done so." Run it to the EP of pc in control of his attention, F/N Cog VGIs. This is called Attention Objective Decision Repetitive.

NOTE: With both these objective attention processes the pc may swear you are hypnotizing him or something. The process actually runs out hypnotism. The pc will come through a band of robotism and come out the other end IN CONTROL OF HIS OWN ATTENTION.

It would never be okay to run Attention Subjective Repetitive on a significance (a no-mass thing). It must be run on a terminal. This is a ONE-SHOT PROCESS, depending for its effectiveness on the correctness of the first item selected.

This item is usually unmistakable in a truly fixated case.

Attention Subjective and Objective Repetitive fits in sequence on the Introspection RD between Steps 6L and 7.

If the terminal connected with the area of fixed attention could not be located then the area could not be addressed with Attention Subjective Repetitive, but in some other manner. It is unlikely that no terminal could be found on a truly fixated attention case.

When a person is released from isolation after terminated handling of a psychotic break it is usual to welcome them back and restore any lost ARC for them from the group, if needed, with an announcement in the OODs.

The person would be interviewed as to whether he wanted to stay or go and what his intentions were.

Formal notification would be made that the person was back in good graces and he would be allowed to make up for any damage done, but not forced to do so. In the case of a crew member, it would be expected he would be assigned to the RPF where there was one, and told to make good.

There is an additional tool for use by the C/S in raising the pc's responsibility. The C/S sends to the pc HCOB 21 Jan. AD 10 JUSTIFICATION with a note asking the pc to please read the HCOB then tell the C/S if it has any application.

This would be done as the first of the series of C/S notes and pc replies on the Cleared Cannibal Step.

If the C/S receives any "rant and rave" in reply he would order it Dated and Located as the pc would be answering out of an incident.

Regardless, the Justification HCOB would have to be followed by O/Ws as the pc has W/Hs there to be restimmed and not running out the O/Ws could cause the TA to skyrocket.

C/Sing and auditing psychos is a very precise and even touchy business. There must be no mistakes and you cannot be heavy-handed on them. They are at the lowest point on the Effect Scale and therefore delicate at best and easily overwhelmed.

It is also policy that a C/S takes it easy on auditors handling psychos. They are very hard to audit and difficult to control. So don't berate the auditor. If they get any kind of a result, three cheers.

It has always been a rule that actions of one RD are not mixed in with another action or used randomly outside of the RD.

Recently I found that a technique from the Introspection RD was used to indicate bypassed charge or something when handling ruds. This is very wrong. This happened in the field as an isolated instance but is worth mentioning.

The integrity of any RD must be maintained or its effectiveness is reduced. When parts of a RD are used at random by a C/S it actually starts the pc on a RD that is left incomplete.

So don't extract bits of this RD and use them on other actions. You would do yourself and the pc a disservice.